Specialized transaction execution via assistive devices

ABSTRACT

Systems, methods, and apparatus are provided for secure transaction execution at an assistive device. Assistive devices include technologies that support people with disabilities in daily tasks, such as mobility aids or vision aids. An assistive device may be preregistered with a financial institution. The financial institution may generate a first hash incorporating a customer identifier and a device identifier. At the time of transaction, an active session may be initiated with the assistive device at a POS terminal, self-service kiosk, or financial institution. The assistive device may use short range wireless communication such as NFC or UWB to transmit the customer identifier and device identifier. A second hash may be generated and compared to the first hash to authenticate the device. Following authentication, the transaction may be completed at the assistive device via user inputs to the assistive device.

FIELD OF TECHNOLOGY

Aspects of the disclosure relate to secure transaction execution via apersonal assistive device.

BACKGROUND OF THE DISCLOSURE

People with disabilities may encounter challenges in the activities ofdaily living. Assistive technology, including assistive, adaptive andrehabilitative devices, can help provide greater independence. Examplesof assistive devices include wheelchairs, walkers, hearing aids, screenreaders and refreshable braille displays.

One area where problems may arise is in the realm of financialtransactions. A customer dependent on assistive technology may facechallenges carrying out a conventional transaction at an automatedteller machine (“ATM”) or at a point of sale (“POS”). The customer mayneed to hand over an access card or payment card to a caregiver orcashier to complete the transaction. However, exposing a card containingsensitive information creates a serious security risk.

It would be desirable to enable an assistive device to interact directlywith a point-of-sale terminal or with financial institution technologyand allow a user to complete a transaction via the assistive device.

SUMMARY OF THE DISCLOSURE

Systems, methods, and apparatus for secure execution of a transactionvia an assistive device are provided.

The assistive device may be registered by a financial institution orother enterprise. A customer identifier and an assistive deviceidentifier may be received at a banking channel. The institution orenterprise may generate a first hash from the customer identifier anddevice identifier. The first hash may be stored in a reference databaseas a reference hash in association with any suitable customeridentification.

At a point of transaction, an active session may be established with theassistive device through short-range wireless communication. Thecustomer identifier and device identifier may be obtained directly fromthe assistive device.

A second hash may be generated from the customer identifier and thedevice identifier and compared with the first hash to authenticate theassistive device.

In response to authentication of the device, transaction data may betransmitted to the assistive device. The transaction may be completedvia an input at the assistive device, such as selection of a paymentinstrument or consent to the transaction. The transaction may beexecuted in response to the input at the assistive device.

In some embodiments, a requirement for entry of a personalidentification number (“PIN”) may be disabled in response toauthentication of the assistive device.

BRIEF DESCRIPTION OF THE DRAWINGS

The objects and advantages of the disclosure will be apparent uponconsideration of the following detailed description, taken inconjunction with the accompanying drawings, in which like referencecharacters refer to like parts throughout, and in which:

FIG. 1 shows illustrative apparatus in accordance with principles of thedisclosure;

FIG. 2 shows illustrative apparatus in accordance with principles of thedisclosure;

FIG. 3 shows an illustrative process flow in accordance with principlesof the disclosure; and

FIG. 4 shows an illustrative process flow in accordance with principlesof the disclosure.

DETAILED DESCRIPTION

Systems, methods, and apparatus for secure execution of a transactionvia an assistive device are provided.

For the sake of illustration, the invention will be described as beingperformed by a “system.” The system may include one or more features ofapparatus and methods that are described herein and/or any othersuitable device or approach.

The system may include an assistive device. Assistive devices includetechnologies that support people with disabilities in daily tasks.Illustrative assistive devices may include mobility aids such as awalker, rollator, electric wheelchair, or power scooter.

Illustrative assistive devices may include vision aids such as a screenreader device, screen magnifier device, or refreshable braille device. Ascreen reader may convert screen content to voice commands and mayaccept voice-based input from a user to select from among the optionspresented. A refreshable braille device may connect wirelessly to acomputer screen and convert screen content to a tactile braille display.

Illustrative assistive devices may include hearing aids or otherwearable technology.

The assistive device may include embedded or partially embedded hardwareand software components. The assistive device may include one or moremicroprocessors. The assistive device may include one or more softwareapplications. The applications may enable the assistive device toexecute various tasks. One or more of the software applications may beexecuted on the processors. Software applications may be stored in amemory embedded in the assistive device.

The assistive device may include one or more displays. The assistivedevice may include one or more communication transceivers. Thecommunication transceivers may be operable to communicate with anexternal processor. The external processor may be located within a POSterminal, a mobile device, a self-service kiosk, a financial institutioncomputer or any other suitable computing device.

The assistive device may include a battery. The battery may beconfigured to power hardware components such as the microprocessor(s).The battery may be rechargeable.

The assistive device may include one or more cameras for capturingimages and/or videos, one or more audio input devices, and one or moreaudio output devices.

Assistive device inputs from a user may be hands-on. Assistive deviceinputs from a user may be hands-free. In some embodiments, assistivedevice inputs may involve a combination of hands-on and hands-freeprotocols.

In some embodiments, the assistive device inputs may be hands-on. Theassistive device may require the use of touch buttons or adaptiveswitches. In some embodiments, the user input may also be entered via atouch screen incorporated into or attached to a frame of the assistivedevice. The touch screen may be a light emitting diode (“LED”) touchscreen. The touch screen may be an organic light emitting diode (“OLED”)touch screen.

The touch screen may receive touch-based user input. Touch-basedgestures may include swiping, tapping, squeezing, and any other suitabletouch-based gestures or combination of touch-based gestures.

In some embodiments, the assistive device inputs may be hands-free. Theassistive device may receive hands-free input through voice commands,eye tracking, gesture recognition, or any other suitable method. Gesturerecognition may include air-based hand and/or body gestures. Air-basedgestures may be performed without touching the assistive device.

The assistive device may include one or more sensors. Illustrativesensors may include a touch screen, camera, accelerometer, gyroscope,and any other suitable sensors. The assistive device sensors may detecthands-free input such as air gestures or eye movement.

The input protocols may be dictated by the structure of the assistivedevice and/or the needs of the user. For example, inputs for mobilityaids may be received via joystick, sip-and-puff controls, head switches,or any suitable method.

The assistive device may include a wireless network interface. Thewireless interface may provide the assistive device with a dedicated,full-time connection to a wireless network. The wireless interface mayimplement the physical layer circuitry necessary for communicating witha data link layer standard, such as Wi-Fi. The wireless interface maysupport input/output (“I/O”), interrupt, direct memory access,interfaces, data transmission, network traffic engineering and/orpartitioning.

The assistive device may include one or more options for short-rangewireless communication. For example, the assistive device may include anactive near field communication (“NFC”) reader configured to establishcontactless communication with a computing device located within apredetermined proximity to the assistive device.

The assistive device may include short-range wireless communication viaBluetooth® technology. Bluetooth® is a short-range wireless technologystandard that is used for exchanging data over short distances using UHFradio waves.

The assistive device may include ultra-wideband (“UWB”) communicationtechnology for short-range data transfer. UWB uses very low energy radiowaves for short-range, high-bandwidth communications.

In some embodiments, the assistive device may be configured to connectto a computing device using a wired communication application. Theassistive device may include a port for attaching a cable to a computingdevice managing a transaction.

The system may enable a user to register an assistive device with afinancial institution or other enterprise. The user may interact withthe financial institution at a variety of banking channels. Illustrativebanking channels include a mobile banking application, an ATM, afinancial center location, or any suitable interface.

The banking channel may obtain customer information from the user. Thecustomer information may include a customer identifier such as a name oraccount number. Other illustrative customer identifiers include customeraddress, access card number, PIN, or any suitable customer identifier.The banking channel may obtain a device name and device identifier fromthe user.

In some embodiments, the banking channel may communicate directly withthe assistive device via short-range wireless communication such as NFCor UWB. The banking channel may receive a customer identifier from thedevice. The banking channel may receive a device name and/or deviceidentifier directly from the assistive device. For additional security,the device identifier may be encoded in the assistive device hardware.For example, the device identifier may be encoded in a microchipembedded in the assistive device.

The financial institution may encrypt the customer data and device data.The banking channel may transmit the customer data and device data to adevice hash generation algorithm. The algorithm may generate a firsthash that incorporates both a customer identifier and the deviceidentifier.

The first hash may be stored as a reference hash in a customer referencedatabase on a bank server, in the cloud, or in any suitable medium. Thereference hash may be stored in association with any suitable customeridentifier.

The system may enable a user to execute transactions via a registeredassistive device. The transactions may be in-person transactions. Thetransactions may be executed at a self-service kiosk, a financialinstitution, a POS, or any suitable location.

At the time of transaction, the device may be authenticated. In oneillustrative embodiment, a POS terminal may establish an active sessionwith the assistive device. The assistive device may transmit customeridentification data and device identification data to the POS terminalusing short-range wireless communication such as NFC, UWB, orBluetooth®.

The POS terminal may transmit the data to a POS transaction server. Adevice hash generation module may be installed at the POS server. Themodule may generate a second hash using the customer data and devicedata obtained from the assistive device at the POS.

The POS transaction server may request the reference hash from thecustomer reference database. A customer verification module may beinstalled at the POS transaction server. The module may perform acomparison of the second hash generated at the POS with the referencehash. Based on the outcome of the comparison, the verification modulemay validate the device hash and authenticate the device to the POSterminal.

In some embodiments, the system may determine a percentage correlationbetween the reference hash and the second hash generated at thetransaction site. If the percentage correlation is below a predeterminedthreshold, the transaction may be completed at the POS terminal. If thepercentage correlation meets or exceeds a predetermined threshold, thetransaction may be completed at the assistive device.

In some embodiments, authentication may be carried out by the financialinstitution instead of a POS system. The POS terminal may transmit thecustomer identification data and device identification data to thefinancial institution. The financial institution may generate a hashusing the customer data and device data obtained from the assistivedevice at the POS. The financial institution may compare the hash withthe reference hash and transmit an authentication result to the POSterminal.

Following authentication, the POS terminal may transmit transaction datato the assistive device. The customer may use the assistive device tocomplete the transaction. For example, the customer may select a paymentoption or approve a payment amount. The transaction data may bedisplayed on a display associated with the assistive device. Thetransaction data may be communicated to the user as an audio output.

Depending on the capabilities of the assistive device, the transactionmay be completed using voice commands, joystick controls, touch screeninputs, eye tracking, or any suitable input method. A transactionprocessing engine may transmit the transaction data to a paymentprocessing system.

The user may input payment instrument information, consent to atransaction or any other suitable information. In some embodiments, theuser may select from stored payment options or from virtual cards in adigital wallet. In some embodiments, a payment instrument may bepreregistered along with the assistive device and stored in thereference database. In some embodiments a customer account identifiedduring registration of the assistive device may be debited for thetransaction.

In some embodiments, a mobile device may be integrated with theassistive device using wireless technology. Illustrative mobile devicesinclude smartphones, tablets, watches, and any other suitable mobiledevice. In some embodiments, the mobile device may be integrated usingwired technology such as a cable or docking cradle. After thetransaction data is transmitted to the authenticated assistive device,the transaction may be completed via input to the integrated mobiledevice.

While the above illustration describes a POS scenario, the assistivedevice may also be authenticated and used to complete a transaction atother locations including a financial institution or a self-servicekiosk such as an ATM. User input at an authenticated assistive devicemay select a transaction option, select a payment instrument or accesscard, deposit, withdraw or transfer funds, select a payment amount,consent to a transaction, or perform any suitable tasks. In someembodiments, user input at an authenticated assistive device may executea digital signature on a document or submit electronic consent to aservice or disclosure.

In some embodiments, PIN or one-time PIN (“OTP”) security features thatare normally associated with a payment method may be disabled followingauthentication of the assistive device. Eliminating PIN or OTPrequirements may streamline transactions and remove additional barriersfor people with disabilities.

In some embodiments, account security features may restrict a paymentinstrument to transactions carried out via the assistive device. Theseadditional security features protect against use of misappropriatedpayment data. Even if an NFC transfer at a POS were to be compromised bya bad actor, the data could not be used for a transaction withoutphysical access to the assistive device.

One or more non-transitory computer-readable media storingcomputer-executable instructions are provided. When executed by aprocessor on a computer system, the instructions may perform a methodfor securely executing a transaction via an assistive device.

The method may include receiving a customer identifier and an assistivedevice identifier at a banking channel and generating a first hash fromthe customer identifier and device identifier. The first hash may bestored in association with any suitable customer identification.

The method may include establishing an active session with the assistivedevice through short-range wireless communication at a point oftransaction. The customer identifier and/or device identifier may beobtained directly from the assistive device. In some embodiments, thecustomer identifier and/or device identifier may be obtained from thecustomer.

The method may include generating a second hash from the customeridentifier and the device identifier and comparing the second hash withthe first hash to authenticate the device.

The method may include, in response to authentication of the device,transmitting transaction data to the assistive device. The method mayinclude receiving an input at the assistive device to complete thetransaction. The input may include selection of a payment instrument,entry of a payment amount, consent to the transaction, or any suitableinput. The transaction may be executed based on the input at theassistive device.

In some embodiments, the method may include disabling a requirement forentry of a PIN in response to authentication of the assistive device.

Systems, methods, and apparatus in accordance with this disclosure willnow be described in connection with the figures, which form a parthereof. The figures show illustrative features of apparatus and methodsteps in accordance with the principles of this disclosure. It is to beunderstood that other embodiments may be utilized, and that structural,functional, and procedural modifications may be made without departingfrom the scope and spirit of the present disclosure.

The steps of methods may be performed in an order other than the ordershown and/or described herein. Method embodiments may omit steps shownand/or described in connection with illustrative methods. Methodembodiments may include steps that are neither shown nor described inconnection with illustrative methods. Illustrative method steps may becombined. For example, an illustrative method may include steps shown inconnection with any other illustrative method.

Apparatus may omit features shown and/or described in connection withillustrative apparatus. Apparatus embodiments may include features thatare neither shown nor described in connection with illustrativeapparatus. Features of illustrative apparatus may be combined. Forexample, an illustrative apparatus embodiment may include features shownor described in connection with another illustrative apparatus/methodembodiment.

FIG. 2 shows an illustrative apparatus 200 that may be configured inaccordance with the principles of the invention.

FIG. 1 shows illustrative apparatus 100 that may be configured inaccordance with the principles of the invention. FIG. 1 is a blockdiagram that illustrates a computing device 101 (alternatively referredto herein as a “server or computer”) that may be used in accordance withthe principles of the invention. The computer server 101 may have aprocessor 103 for controlling overall operation of the server and itsassociated components, including RAM 105, ROM 107, input/output (“I/O”)module 109, and memory 115.

I/O module 109 may include a microphone, keypad, touchscreen and/orstylus through which a user of device 101 may provide input, and mayalso include one or more of a speaker for providing audio output and avideo display device for providing textual, audiovisual and/or graphicaloutput. Software may be stored within memory 115 and/or other storage(not shown) to provide instructions to processor 103 for enabling server101 to perform various functions. For example, memory 115 may storesoftware used by server 101, such as an operating system 117,application programs 119, and associated database 111.

Alternatively, some or all of computer executable instructions of server101 may be embodied in hardware or firmware (not shown).

Server 101 may operate in a networked environment supporting connectionsto one or more remote computers, such as terminals 141 and 151.Terminals 141 and 151 may be personal computers or servers that includemany or all of the elements described above relative to server 101. Thenetwork connections depicted in FIG. 1 include a local area network(LAN) 125 and a wide area network (WAN) 129, but may also include othernetworks.

When used in a LAN networking environment, computer 101 is connected toLAN 125 through a network interface or adapter 113.

When used in a WAN networking environment, server 101 may include amodem 127 or other means for establishing communications over WAN 129,such as Internet 131.

It will be appreciated that the network connections shown areillustrative and other means of establishing a communications linkbetween the computers may be used. The existence of any of variouswell-known protocols such as TCP/IP, Ethernet, FTP, HTTP and the like ispresumed, and the system may be operated in a client-serverconfiguration to permit a user to retrieve web pages from a web-basedserver. Any of various conventional web browsers may be used to displayand manipulate data on web pages.

Additionally, application program 119, which may be used by server 101,may include computer executable instructions for invoking userfunctionality related to communication, such as email, short messageservice (SMS), authentication services and voice input and speechrecognition applications.

Computing device 101 and/or terminals 141 or 151 may also be mobileterminals including various other components, such as a battery,speaker, and antennas (not shown). Terminal 151 and/or terminal 141 maybe portable devices such as a laptop, tablet, smartphone or any othersuitable device for receiving, storing, transmitting and/or displayingrelevant information.

Any information described above in connection with database 111, and anyother suitable information, may be stored in memory 115. One or more ofapplications 119 may include one or more algorithms that encryptinformation, process received executable instructions, interact withenterprise systems, perform power management routines or other suitabletasks. Algorithms may be used to perform the functions of one or more ofregistering an assistive device, authenticating an assistive device,generating a first hash, generating a second hash, comparing the firsthash and the second hash, and/or perform any other suitable tasks.

The invention may be operational with numerous other general purpose orspecial purpose computing system environments or configurations.Examples of well-known computing systems, environments, and/orconfigurations that may be suitable for use with the invention include,but are not limited to, personal computers, server computers, hand-heldor laptop devices, tablets, mobile phones and/or other personal digitalassistants (“PDAs”), multiprocessor systems, microprocessor-basedsystems, set top boxes, programmable consumer electronics, network PCs,minicomputers, mainframe computers, distributed computing environmentsthat include any of the above systems or devices, and the like.

The invention may be described in the general context ofcomputer-executable instructions, such as program modules, beingexecuted by a computer. Generally, program modules include routines,programs, objects, components, data structures, etc. that performparticular tasks or implement particular abstract data types. Theinvention may also be practiced in distributed computing environmentswhere tasks are performed by remote processing devices that are linkedthrough a communications network. In a distributed computingenvironment, program modules may be located in both local and remotecomputer storage media including memory storage devices.

FIG. 2 shows an illustrative apparatus 200 that may be configured inaccordance with the principles of the invention.

Apparatus 200 may be a computing machine. Apparatus 200 may include oneor more features of the apparatus that is shown in FIG. 1 .

Apparatus 200 may include chip module 202, which may include one or moreintegrated circuits, and which may include logic configured to performany other suitable logical operations.

Apparatus 200 may include one or more of the following components: I/Ocircuitry 204, which may include a transmitter device and a receiverdevice and may interface with fiber optic cable, coaxial cable,telephone lines, wireless devices, PHY layer hardware, a keypad/displaycontrol device or any other suitable encoded media or devices;peripheral devices 206, which may include counter timers, real-timetimers, power-on reset generators or any other suitable peripheraldevices; logical processing device 208, which may register an assistivedevice, authenticate an assistive device, generate a hash based oncustomer and device identifiers, and perform other methods describedherein; and machine-readable memory 210.

Machine-readable memory 210 may be configured to store inmachine-readable data structures: customer data, device data, hash data,transaction data, and any other suitable information or data structures.

Components 202, 204, 206, 208 and 210 may be coupled together by asystem bus or other interconnections 212 and may be present on one ormore circuit boards such as 220. In some embodiments, the components maybe integrated into a single chip. The chip may be silicon-based.

FIG. 3 shows illustrative process flow 300 for transaction execution viaa power-driven wheelchair. While the illustrative use case involves awheelchair, the invention is operable with a variety of assistivedevices, as set forth above.

Elements 302-306 illustrate registration of the wheelchair. A user mayregister the wheelchair at banking channels 302. Illustrative bankingchannels shown include a mobile banking application, financial centerand ATM, but any suitable channel may be used. Banking channels 302 mayreceive customer information such as a name or account number. Bankingchannels 302 may interact with the wheelchair to determine a deviceidentifier. Device hash generator 304 may apply one or more hashingalgorithms to generate a reference hash that incorporates the customeridentifier and the device identifier. The reference hash may be storedin reference database 306.

Elements 308-318 illustrate transaction execution at a POS using theregistered wheelchair. While the illustrative use case involves a POStransaction, the invention is operable in a variety of transactionscenarios, as set forth above.

Elements 308-314 illustrate authentication of the wheelchair. POSterminal 308 may initiate an active session with the wheelchair andretrieve the customer identifier and device identifier. In someembodiments, the active session may be initiated at the wheelchairthrough voice, touch, or gesture inputs, through manipulation of ajoystick, or by any suitable method.

POS terminal 308 may transmit the customer identifier and deviceidentifier to POS transaction server 310. POS transaction server 310 mayretrieve the reference hash from reference database 306. Device hashgeneration module 312 may generate a new hash from the customeridentifier and device identifier obtained at the POS. Device hashauthentication module 312 may compare the new hash to the reference hashto authenticate the wheelchair.

The authentication may be transmitted to POS terminal 308. POS terminal308 may communicate transaction data to a display integrated into thewheelchair. The wheelchair may display the transaction information. Thewheelchair may receive an input from the user selecting a paymentinstrument or confirming the transaction. The input may be transmittedto POS device transaction processing engine 316. The completedtransaction data may be transmitted to payment processing system 318 forprocessing.

In some embodiments (not shown), the input may be transmitted to POSterminal 308. POS terminal 308 may transmit transaction information toPOS device transaction processing 316 or payment processing system 318.

FIG. 4 shows illustrative process flow 400 for transaction execution viaan assistive device at an ATM.

At step 402, an assistive device is registered with a financialinstitution. At step 404 a reference hash is generated based on acustomer identifier and a device identifier obtained from the assistivedevice. The reference hash may be stored. The reference hash may be ahardware-based reference hash and the device identifier may be encodedinto the assistive device.

At step 406, the customer initiates an active session at an ATM. Thedevice may use short-term wireless transmission to provide a customeridentifier and a device identifier directly to the ATM. At step 408, anew hash may be generated using the data obtained by the ATM.

At step 410, the new hash may be compared to the reference hash. At step412, authentication may be determined based on the comparison. At step414, if the assistive device is not authenticated, the transaction maycontinue at the ATM. At step 416, if the assistive device isauthenticated, transaction data may be transmitted to the assistivedevice. At step 418, the transaction may be completed at the assistivedevice.

Thus, methods and apparatus for SPECIALIZED TRANSACTION EXECUTION VIAASSISTIVE DEVICES are provided. Persons skilled in the art willappreciate that the present invention can be practiced by other than thedescribed embodiments, which are presented for purposes of illustrationrather than of limitation, and that the present invention is limitedonly by the claims that follow.

What is claimed is:
 1. A method for secure transaction execution at anelectric personal assistive mobility device, the method comprising: at afinancial institution interface: receiving a customer identifier;receiving a mobility device identifier, the mobility device identifierencoded in hardware embedded in the mobility device; generating a firsthash from the customer identifier and the mobility device identifier;and storing the first hash in a reference database in association withthe customer identifier; and at a point of sale (POS): establishing anactive session with the mobility device through short-range wirelesscommunication, the mobility device being configured to communicate witha POS terminal at the POS using near field communication (NFC);receiving the customer identifier and the mobility device identifierfrom the mobility device; generating a second hash from the customeridentifier and the mobility device identifier; transmitting a request tothe financial institution for the first hash; comparing the second hashto the first hash to authenticate the mobility device; and when apercentage correlation between the second hash and the first hash meetsor exceeds a predetermined threshold: routing transaction data to adisplay integrated into the mobility device; and executing thetransaction based at least in part on an input at the mobility device.2. The method of claim 1, wherein a POS terminal is configured totransmit the customer identifier and mobility device identifier receivedfrom the mobility device to a POS transaction server for authenticationof the mobility device.
 3. The method of claim 2, wherein the POStransaction server comprises a device hash generation module.
 4. Themethod of claim 1, wherein the input at the mobility device comprisesconsent to the transaction.
 5. The method of claim 4, wherein consent tothe transaction is entered using a mobility device joystick.
 6. Themethod of claim 1, further comprising, when the percentage correlationbetween the second hash and the first hash meets or exceeds apredetermined threshold, disabling a requirement for entry of a personalidentification number (PIN).
 7. The method of claim 1, furthercomprising restricting use of a payment instrument to transactionsexecuted via the mobility device.
 8. One or more non-transitorycomputer-readable media storing computer-executable instructions which,when executed by a processor on a computer system, perform a method forsecurely executing a transaction at a power-assisted mobility aid, themethod comprising: receiving a customer identifier at a banking channel;receiving a mobility aid identifier at the banking channel, the mobilityaid identifier encoded in hardware embedded in the mobility aid;generating a first hash from the customer identifier and the mobilityaid identifier; and storing the first hash in a reference database inassociation with the customer identifier; establishing an active sessionwith the mobility aid through short-range wireless communication at apoint of sale (POS); receiving the customer identifier and the mobilityaid identifier from the mobility aid at a POS terminal located at thePOS via short-range wireless data transfer, the mobility aid beingconfigured to communicate with the POS terminal using ultra-wide bandcommunication; generating a second hash from the customer identifier andthe mobility aid identifier; comparing the second hash to the first hashto authenticate the mobility aid; and when a percentage correlationbetween the second hash and the first hash meets or exceeds apredetermined threshold: routing transaction data to a displayintegrated into the mobility aid; and executing the transaction inresponse to an input at the mobility aid.
 9. The media of claim 8,wherein the POS terminal is configured to transmit the customeridentifier and mobility aid identifier to a POS transaction server forauthentication of the mobility aid.
 10. The media of claim 9, whereinthe POS transaction server comprises a device hash generation module.11. The media of claim 8, wherein the input at the mobility aidcomprises consent to the transaction.
 12. The media of claim 11, whereinconsent to the transaction is received via voice-based input.
 13. Themedia of claim 8, further comprising, when the percentage correlationbetween the second hash and the first hash meets or exceeds apredetermined threshold, disabling a requirement for entry of a personalidentification number (PIN).
 14. The media of claim 8, furthercomprising restricting use of a payment instrument to transactionsexecuted via the mobility aid.